Fixed issues #107 and #123. The receiver now checks the connection status when popping a message fails, and calls the reconnect function if the connection check indicates that the connection is down. The root cause of the receiver's failure to pop a message is that the sender process invokes force_push() when it fails to push data into the circular queue. The force_push() function then identifies which receiver has not read the data and disconnects it. Typically, the receiver process hasn't read the data because it is either blocked (e.g., paused at a breakpoint) or stuck (when the system CPU load is high). Consequently, the receiver process has no way of knowing whether the connection was disconnected and will either wait on ::SignalObjectAndWait (when there is only one receiver in the connection) or endlessly retry popping the message.

Therefore, the solution involves making the receiver aware of disconnections so it can take action to recover, such as calling the reconnect() function. To achieve this, I have optimized the connect function and added reconnection logic in the recv() function. This approach has proven effective.